-
-
Notifications
You must be signed in to change notification settings - Fork 431
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Expose zlib constants for backwards compat #747 #750
base: develop
Are you sure you want to change the base?
Conversation
7f76835
to
f1f89a3
Compare
f1f89a3
to
25ff004
Compare
From the CI: D:\a\minizip-ng\minizip-ng\mz_compat.h(19,10): fatal error C1083: Cannot open include file: 'zlib.h':
No such file or directory [D:\a\minizip-ng\minizip-ng\test\gtest_minizip.vcxproj] |
I could be wrong, but I think this CMake: Lines 713 to 714 in ef3ef9a
needs to add |
Should I wait on this PR to make a new release? |
Building a project that had an internal copy of minizip 1.x, but preferring an external library, with minizip 4.x showed that the compat layer was not exposing some constants from zlib that minizip 1.x headers did.
25ff004
to
0f8cf66
Compare
Go for 4.0.4. |
For information, minizip-ng 4.0.7 has been released (2024-06-15). |
$<BUILD_INTERFACE:${CMAKE_CURRENT_BINARY_DIR}> | ||
${ZLIB_SOURCE_DIR} | ||
${ZLIB_BINARY_DIR}) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
From my experiments, that part isn't needed. It's actually causing extra build issues (for Windows).
I came up with a solution that builds in #815
Building a project that had an internal copy of minizip 1.x, but
preferring an external library, with minizip 4.x showed that the
compat layer was not exposing some constants from zlib that
minizip 1.x headers did.